Why

Follow-up to #14406, which made blockifier_reexecution compile Sierra→Casm in-process. Both Docker images that build on it shipped the starknet-sierra-compile sidecar binary purely for that path; it is now dead weight.

What

• crates/starknet_transaction_prover/Dockerfile: the prover is built --features stwo_proving (cairo_native disabled), so Sierra→Casm was its only compiler dependency. Removed the install_compiler_binaries.sh --sierra step, the CARGO_TOOLS_ROOT env, and the COPY of the tools tree. The runtime image is now a single self-contained binary — no compiler sidecar at all.
• crates/blockifier_reexecution/replay/Dockerfile: built --features cairo_native, so it still needs starknet-native-compile (the compare-native path, unaffected by blockifier_reexecution: compile Sierra to Casm in-process via library call #14406). Switched the install from both compilers to --native only; kept the tools COPY and the binutils/libc6-dev runtime deps that starknet-native-compile requires. Comments updated accordingly.

Validation

• docker build --check on both Dockerfiles — "Check complete, no warnings found."
• scripts/install_compiler_binaries.sh --native is a supported standalone invocation; the replay base stage installs LLVM 19, so its llvm-config-19 gate passes.
• The prover's zero-compiler runtime was already demonstrated under blockifier_reexecution: compile Sierra to Casm in-process via library call #14406 (the bare binary starts and serves with no compiler binary present anywhere).
• Both images are built by CI on the PR (starknet_transaction_prover_ci.yml docker-build; blockifier_reexecution_docker_publish.yml), giving a full end-to-end build.

Stacked on #14406.

🤖 Generated with Claude Code